Triple
T13483376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zora Folley |
E318429
|
entity |
| Predicate | titleChallengeDate |
P94738
|
FINISHED |
| Object | 1967-03-22 |
—
|
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: 1967-03-22 | Statement: [Zora Folley, titleChallengeDate, 1967-03-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleChallengeDate Context triple: [Zora Folley, titleChallengeDate, 1967-03-22]
-
A.
challengeType
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
B.
titleDate
chosen
Indicates the date associated with a title, such as when it was granted, recorded, or became effective.
-
C.
challengeUndertaken
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
-
D.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
E.
virtualChallengeDate
Indicates the date on which a virtual challenge or competition is scheduled to occur or recorded as having taken place.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3868ec8190a6a1803018d4f2d8 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.