Triple
T16416463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Sipe |
E398697
|
entity |
| Predicate | teamLed |
P87490
|
FINISHED |
| Object | Cleveland Browns 1980 |
—
|
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: Cleveland Browns 1980 | Statement: [Brian Sipe, teamLed, Cleveland Browns 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLed Context triple: [Brian Sipe, teamLed, Cleveland Browns 1980]
-
A.
ledTeamTo
Indicates that one entity acted as a leader or guiding force that directed a team toward achieving a particular goal, outcome, or success.
-
B.
ledTeamIn
chosen
Indicates that one entity had primary leadership responsibility over a team in which the other entity participated or was involved.
-
C.
teamComponent
Indicates that one entity functions as a component, member, or sub-unit within a larger team or group entity.
-
D.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
-
E.
teamLead
Indicates that one entity serves as the leader or primary coordinator of a team that includes the other entity.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32877ff248190886717d3329421a7 |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.