Triple
T30597377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Brevoort |
E778823
|
entity |
| Predicate | worksForUniverse |
P179945
|
FINISHED |
| Object | Marvel Universe |
—
|
NE NERFINISHED |
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: Marvel Universe | Statement: [Tom Brevoort, worksForUniverse, Marvel Universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksForUniverse Context triple: [Tom Brevoort, worksForUniverse, Marvel Universe]
-
A.
worksOnPlatform
Indicates that an entity performs its functions, operations, or activities using or within a specified platform.
-
B.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
C.
isUniversalFor
Indicates that something applies to or is valid for all members of a given set, domain, or context without exception.
-
D.
isUniversalFor
Indicates that a property, rule, or condition holds true for all members of a specified set or domain without exception.
-
E.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
- F. None of above. chosen
Provenance (4 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 29, 2026, 8:24 p.m.