Triple
T6198571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akashi Kaikyo Bridge |
E138571
|
entity |
| Predicate | recordHeldFor |
P69615
|
FINISHED |
| Object | longest suspension bridge main span |
—
|
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: longest suspension bridge main span | Statement: [Akashi Kaikyo Bridge, recordHeldFor, longest suspension bridge main span]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordHeldFor Context triple: [Akashi Kaikyo Bridge, recordHeldFor, longest suspension bridge main span]
-
A.
recordHeldIn
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
B.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
C.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
D.
recordHeldUntil
Indicates that a record remained valid, in force, or applicable up to a specified end time or condition.
-
E.
recordBrokenPreviouslyHeldBy
Indicates that a new record has surpassed and replaced a prior record that was previously held by another entity.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06251b47881909bd8d2ea37541959 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:20 p.m.