Triple
T4348954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosetta Stone |
E97972
|
entity |
| Predicate | enteredCollection |
P55668
|
FINISHED |
| Object | British Museum in 1802 |
—
|
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: British Museum in 1802 | Statement: [Rosetta Stone, enteredCollection, British Museum in 1802]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCollection Context triple: [Rosetta Stone, enteredCollection, British Museum in 1802]
-
A.
enteredIntoBy
Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
-
B.
formerCollectionOf
Indicates that an entity once served as a collection or repository for another entity, but no longer holds that role.
-
C.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
D.
enteredStatus
Indicates that an entity has transitioned into or assumed a particular status or state.
-
E.
hasCollectionFrom
Indicates that an entity possesses or maintains a collection that originates from, or is sourced from, another specified entity.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a6e89c8190b9bf2cccb63839b3 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:15 p.m.