Triple
T36995930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invisible Stripes |
E915226
|
entity |
| Predicate | hasGeorgeRaftRole |
P196134
|
FINISHED |
| Object | Cliff Taylor |
E2211120
|
NE 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: Cliff Taylor | Statement: [Invisible Stripes, hasGeorgeRaftRole, Cliff Taylor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeorgeRaftRole Context triple: [Invisible Stripes, hasGeorgeRaftRole, Cliff Taylor]
-
A.
hasPrimaryElectionRole
Indicates that an entity holds a main or leading role in conducting, overseeing, or participating in a primary election.
-
B.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
C.
hasLeaderParticipant
Indicates that an entity participates in an event or activity in the role of a leader.
-
D.
hasQuorum
Indicates that the number of required participants or members is sufficient to validly conduct the specified activity or decision.
-
E.
hasPrimaryCoordinator
Indicates that one entity serves as the main or lead coordinator responsible for organizing or managing another entity.
- F. None of above. chosen
Provenance (5 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdae405481909c4896c31b4adb27 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
| PDg | Predicate description generation | batch_69fe08d1b3f881908eccb74cb0d246dc |
completed | May 8, 2026, 4:01 p.m. |
Created at: May 3, 2026, 4:14 p.m.