Triple
T32419363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Chop 2 |
E828408
|
entity |
| Predicate | hasTrackMaker |
P198882
|
FINISHED |
| Object | Young Chop |
—
|
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: Young Chop | Statement: [King Chop 2, hasTrackMaker, Young Chop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackMaker Context triple: [King Chop 2, hasTrackMaker, Young Chop]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
hasTrackControl
Indicates that one entity has authority or capability to manage, direct, or regulate the operation or behavior of another entity’s track or tracking process.
-
C.
hasTrackFacility
Indicates that one entity provides or includes a track facility (such as a running or racing track) available for use by another entity.
-
D.
hasTrackSurface
Indicates that an entity (such as a track) possesses or is characterized by a particular type of surface.
-
E.
hasTailTracks
Indicates that an entity exhibits or leaves behind tail-shaped tracks or imprints as evidence of its movement or presence.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: May 1, 2026, 12:54 a.m.