Triple
T16128393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pero Cameron |
E391329
|
entity |
| Predicate | captaincyPeriodApprox |
P118779
|
FINISHED |
| Object | late 1990s to mid-2000s |
—
|
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: late 1990s to mid-2000s | Statement: [Pero Cameron, captaincyPeriodApprox, late 1990s to mid-2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captaincyPeriodApprox Context triple: [Pero Cameron, captaincyPeriodApprox, late 1990s to mid-2000s]
-
A.
captaincyPeriod
chosen
Indicates the time span during which an entity serves as the captain of a team, group, or vessel.
-
B.
captaincyStartYear
Indicates the year in which an entity first assumed the role of captain.
-
C.
captaincyEndYear
Indicates the year in which an entity’s period of serving as captain comes to an end.
-
D.
captaincyPrecedes
Indicates that one captaincy role or tenure occurs earlier in time than another captaincy role or tenure.
-
E.
servedAsCaptainFrom
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20206a6f08190aa648d2bb11e7878 |
completed | April 17, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.