Triple
T7892988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adams family tomb |
E183281
|
entity |
| Predicate | burialChamberCount |
P1545
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Adams family tomb, burialChamberCount, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialChamberCount Context triple: [Adams family tomb, burialChamberCount, 1]
-
A.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
B.
numberOfChambers
chosen
Indicates the count of distinct chambers or compartments associated with an entity.
-
C.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
D.
chamberOfFinalPassage
Indicates a relationship where a location serves as the last or decisive venue through which something (such as legislation, a process, or a journey) must pass before completion or enactment.
-
E.
tombNumber
Indicates the specific identifying number assigned to a particular tomb within a set of tombs.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a008fb88190a039fec40483ab93 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5 p.m.