Triple
T4042078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace Bridge |
E83972
|
entity |
| Predicate | hasNightlyRaising |
P53762
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Palace Bridge, hasNightlyRaising, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNightlyRaising Context triple: [Palace Bridge, hasNightlyRaising, yes]
-
A.
canRaise
Indicates that one entity has the ability or authority to increase, elevate, or lift another entity (such as a value, object, or status).
-
B.
raisedDuring
Indicates that one entity was brought up, nurtured, or developed within the time period or circumstances defined by another entity.
-
C.
raisedWith
Indicates that two or more entities grew up together in the same household or close environment during their formative years.
-
D.
risesIn
Indicates that a river or similar watercourse originates or begins its flow in a specified location.
-
E.
raisedAt
Indicates that something was brought up, mentioned, or initiated at a particular time, place, or contextual point.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb5b65c08190ba3f340ed18737f8 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.