Triple
T14569586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolbrom |
E341873
|
entity |
| Predicate | mayBeNamedAfter |
P92520
|
FINISHED |
| Object | founder Wolfram or Wolborz |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: founder Wolfram or Wolborz | Statement: [Wolbrom, mayBeNamedAfter, founder Wolfram or Wolborz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeNamedAfter Context triple: [Wolbrom, mayBeNamedAfter, founder Wolfram or Wolborz]
-
A.
nameMayReferTo
chosen
Indicates that a given name or label can ambiguously denote or be used for one or more possible entities.
-
B.
hasPartiallyNamedAfter
Indicates that one entity is partially named in reference to another entity, such that only a portion of its name derives from or honors the other.
-
C.
notNamedAfter
Indicates that one entity is explicitly not named in honor of, or derived from the name of, another entity.
-
D.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
E.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f2121481908f2385637944785d |
completed | April 14, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.