Triple
T29692505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skull 5 |
E751247
|
entity |
| Predicate | hasBrowridge |
P176743
|
FINISHED |
| Object | massive browridge |
—
|
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: massive browridge | Statement: [Skull 5, hasBrowridge, massive browridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrowridge Context triple: [Skull 5, hasBrowridge, massive browridge]
-
A.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
hasBridgeView
Indicates that one entity provides a view of, or overlooking, a bridge from its location or perspective.
-
C.
hasBridgeStyle
Indicates that a bridge is characterized by a particular architectural or structural style.
-
D.
hasBridgeAccess
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
-
E.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 28, 2026, 7:18 p.m.