Triple
T38011751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynette |
E948380
|
entity |
| Predicate | laterRespects |
P203337
|
FINISHED |
| Object | Gareth |
—
|
NE NERFINISHED |
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: Gareth | Statement: [Lynette, laterRespects, Gareth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRespects Context triple: [Lynette, laterRespects, Gareth]
-
A.
laterBasedOn
Indicates that one event, state, or version occurs or is established after another, using the earlier one as its basis or reference point.
-
B.
laterPolicy
Indicates that one policy occurs or becomes effective after another policy in time.
-
C.
laterRule
Indicates that one rule occurs, is applied, or takes effect after another rule in a defined ordering or sequence.
-
D.
laterCorrespondsTo
Indicates that one entity corresponds to, matches, or is the counterpart of another entity that occurs or is defined at a later time or stage.
-
E.
laterPermittedBy
Indicates that an action or state becomes allowed at a later time due to a specific permission, rule, or authority.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
| PDg | Predicate description generation | batch_6a0163359e588190ba365f65b2d86435 |
completed | May 11, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.