Triple
T1018275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Académie royale d’architecture |
E21980
|
entity |
| Predicate | taughtDiscipline |
P13197
|
FINISHED |
| Object | architectural drawing |
—
|
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: architectural drawing | Statement: [Académie royale d’architecture, taughtDiscipline, architectural drawing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taughtDiscipline Context triple: [Académie royale d’architecture, taughtDiscipline, architectural drawing]
-
A.
isTaughtAs
chosen
Indicates that something is presented or delivered as instructional content, typically within an educational or training context.
-
B.
taughtAs
Indicates that one entity served as a teacher or instructor for another entity in an educational or training context.
-
C.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
D.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
E.
subDisciplineOf
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
- F. None of above.
Provenance (3 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c6005081909d9e56114c532d14 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.