Triple
T268089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Crane Tower |
E5775
|
entity |
| Predicate | designedToEvok |
P2340
|
FINISHED |
| Object | ancient tower appearance |
—
|
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: ancient tower appearance | Statement: [Yellow Crane Tower, designedToEvok, ancient tower appearance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToEvok Context triple: [Yellow Crane Tower, designedToEvok, ancient tower appearance]
-
A.
designedToEvoke
chosen
Indicates that something was intentionally created or arranged in order to elicit a particular reaction, feeling, or response from an audience or observer.
-
B.
envisionedAs
Indicates that one entity is mentally pictured, imagined, or conceived in terms of another entity or role.
-
C.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
D.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
E.
eveCelebrationOn
Indicates that an event or entity is engaged in or associated with a celebration occurring on a specific date or occasion.
- F. None of above.
Provenance (3 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25dae4a0c8190a66cf6ed3889851c |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b70d99c819085d8381a313a2a34 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.