Triple
T28443834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Your Face or Mine? |
E715782
|
entity |
| Predicate | firstRunStartDate |
P201718
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Your Face or Mine?, firstRunStartDate, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunStartDate Context triple: [Your Face or Mine?, firstRunStartDate, 2002]
-
A.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
-
B.
firstRunTimePeriod
Indicates the initial time span or interval during which something first occurs, operates, or is in effect.
-
C.
firstInvocationDate
Indicates the date on which the entity was first invoked, used, or called for the first time.
-
D.
firstSessionStartTime
Indicates the timestamp when an entity’s initial or very first session begins.
-
E.
firstPerformedOn
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
- F. None of above. chosen
Provenance (4 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_6a0018cebf688190bbd90ac79d250182 |
completed | May 10, 2026, 5:34 a.m. |
Created at: April 28, 2026, 1:47 a.m.