Triple
T1955303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent Diamond |
E42253
|
entity |
| Predicate | mountedIn |
P10139
|
FINISHED |
| Object | crown of Louis XV |
—
|
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: crown of Louis XV | Statement: [Regent Diamond, mountedIn, crown of Louis XV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountedIn Context triple: [Regent Diamond, mountedIn, crown of Louis XV]
-
A.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
B.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
C.
installedBy
Indicates that one entity was set up, put in place, or made operational through the actions or intervention of another entity.
-
D.
integratedIn
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
-
E.
attachedTo
chosen
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb353aa8c81909810347f9981a02f |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.