Triple
T36208677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pat Patterson |
E1047471
|
entity |
| Predicate | returnedToRing |
P192096
|
FINISHED |
| Object | occasional matches in the late 1990s and 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: occasional matches in the late 1990s and 2000s | Statement: [Pat Patterson, returnedToRing, occasional matches in the late 1990s and 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToRing Context triple: [Pat Patterson, returnedToRing, occasional matches in the late 1990s and 2000s]
-
A.
returnedToUse
Indicates that something previously inactive, unavailable, or discontinued has been put back into active use or operation.
-
B.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
-
C.
returnedToPort
Indicates that an entity has come back to its home or designated port after being away.
-
D.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
E.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:09 p.m.