Triple
T8391317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porte Saint-Martin |
E197948
|
entity |
| Predicate | hasMainArch |
P81957
|
FINISHED |
| Object | central carriageway arch |
—
|
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: central carriageway arch | Statement: [Porte Saint-Martin, hasMainArch, central carriageway arch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainArch Context triple: [Porte Saint-Martin, hasMainArch, central carriageway arch]
-
A.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
B.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
C.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional system.
-
D.
hasMainSource
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
E.
hasArchType
Indicates that one entity possesses or is characterized by a particular architectural type or style.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb810c5c5c81908e124c64911c4e6c |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:03 p.m.