Triple
T35452668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zack Brown |
E1024678
|
entity |
| Predicate | formsProductionTeamWith |
P151320
|
FINISHED |
| Object | Miri Linky |
—
|
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: Miri Linky | Statement: [Zack Brown, formsProductionTeamWith, Miri Linky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsProductionTeamWith Context triple: [Zack Brown, formsProductionTeamWith, Miri Linky]
-
A.
sharesProductionTeamWith
Indicates that two entities are produced or created by at least one of the same production team members or organizations.
-
B.
developmentTeamFor
Indicates the team responsible for developing or building a particular product, project, or system.
-
C.
designTeamFrom
Indicates that a design team originates from, is based in, or is associated with a specified source entity or location.
-
D.
organizedTeam
chosen
Indicates that an entity has formed, structured, or coordinated a group of individuals to function together as a team.
-
E.
fromProduction
Indicates that something originates from, is derived from, or is produced by a particular production process, source, or facility.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:04 p.m.