Triple
T26892872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahasthangarh |
E677821
|
entity |
| Predicate | artifactsInclude |
P33054
|
FINISHED |
| Object | beads |
—
|
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: beads | Statement: [Mahasthangarh, artifactsInclude, beads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artifactsInclude Context triple: [Mahasthangarh, artifactsInclude, beads]
-
A.
featuresArtifactsFrom
Indicates that one entity includes, presents, or showcases artifacts that originate from or are associated with another entity.
-
B.
includesArtBy
Indicates that one entity contains, features, or presents artwork created by another entity.
-
C.
outputIncludes
Indicates that the result or product of a process, function, or action contains or incorporates a specified element or component.
-
D.
featuresArtifact
chosen
Indicates that one entity prominently includes, presents, or showcases another entity as an artifact.
-
E.
sourcesInclude
Indicates that one entity’s content, data, or information is derived from, references, or incorporates material from another specified source.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:46 a.m.