Triple
T32343710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mound 11 |
E826393
|
entity |
| Predicate | hasNumberWithinSite |
P76556
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Mound 11, hasNumberWithinSite, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberWithinSite Context triple: [Mound 11, hasNumberWithinSite, 11]
-
A.
numberWithinSite
chosen
Indicates that an entity has a specific identifying number or position assigned within the context of a particular site or location.
-
B.
isOnSiteWith
Indicates that two or more entities are physically present at the same site or location at the same time.
-
C.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
-
D.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
E.
hasSiteCode
Indicates that an entity is associated with a specific site identifier or code used to distinguish its location or facility.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 1, 2026, 12:48 a.m.