Triple
T35445319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salon of 1717 |
E1024465
|
entity |
| Predicate | organizedByType |
P193087
|
FINISHED |
| Object | royal academy |
—
|
NE NERFINISHED |
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: royal academy | Statement: [Salon of 1717, organizedByType, royal academy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedByType Context triple: [Salon of 1717, organizedByType, royal academy]
-
A.
organizedFrom
Indicates that something has been arranged, structured, or formed starting from a specified source or initial set of elements.
-
B.
fullyOrganizedBy
Indicates that an event, activity, or process is completely planned, coordinated, and managed by a specified organizing entity.
-
C.
organizeBy
Indicates arranging or structuring items or entities according to a specified criterion, category, or ordering principle.
-
D.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
-
E.
organizedWith
Indicates that entities are arranged, structured, or coordinated together as part of the same organizing scheme or effort.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 3, 2026, 4:04 p.m.