Triple
T31301680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Did Something Bad |
E798228
|
entity |
| Predicate | hasReputationTourVisuals |
P203154
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [I Did Something Bad, hasReputationTourVisuals, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReputationTourVisuals Context triple: [I Did Something Bad, hasReputationTourVisuals, true]
-
A.
hasTouringReputation
Indicates that an entity is recognized or reputed for its activities, performance, or presence while traveling or touring.
-
B.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
C.
hasTourAccess
Indicates that an entity is permitted to enter or participate in a specified tour.
-
D.
hasTourElement
Indicates that something includes or is associated with a specific element or component of a tour.
-
E.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01295195748190b896d99c3d1f6134 |
completed | May 11, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_6a0128fe96dc8190a73715ab08752dd1 |
completed | May 11, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_6a012950e8d48190a9dc1105fe7a5fb3 |
completed | May 11, 2026, 12:56 a.m. |
Created at: April 29, 2026, 9:14 p.m.