Triple
T19532306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Palo Alto |
E488684
|
entity |
| Predicate | useAfterDamage |
P136675
|
FINISHED |
| Object | fishing pier attraction |
—
|
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: fishing pier attraction | Statement: [SS Palo Alto, useAfterDamage, fishing pier attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useAfterDamage Context triple: [SS Palo Alto, useAfterDamage, fishing pier attraction]
-
A.
actedDespiteWounds
Indicates that an entity performed an action or fulfilled a role even though it was wounded or injured at the time.
-
B.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
C.
sufferedDamageTo
Indicates that one entity has experienced harm, loss, or deterioration affecting another entity or one of its parts.
-
D.
damageLeadsTo
Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
-
E.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363fd1f8819080805346efad2579 |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.