Triple
T8730988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Paul-Saint-Louis Church |
E207252
|
entity |
| Predicate | hasNavePlan |
P84327
|
FINISHED |
| Object | Latin cross plan |
—
|
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: Latin cross plan | Statement: [Saint-Paul-Saint-Louis Church, hasNavePlan, Latin cross plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavePlan Context triple: [Saint-Paul-Saint-Louis Church, hasNavePlan, Latin cross plan]
-
A.
hasNave
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
-
B.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
-
C.
hasShuttlecraft
Indicates that an entity possesses, controls, or is equipped with one or more shuttlecraft.
-
D.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
E.
hasPlanner
Indicates that an entity is associated with or assigned a planner responsible for organizing or managing its activities or processes.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d27efb88190b42d5bc9774d9c63 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:37 p.m.