Triple
T16292803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fang people |
E395566
|
entity |
| Predicate | useObject |
P5510
|
FINISHED |
| Object | Byeri reliquary box |
—
|
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: Byeri reliquary box | Statement: [Fang people, useObject, Byeri reliquary box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useObject Context triple: [Fang people, useObject, Byeri reliquary box]
-
A.
usesFoundObject
Indicates that an entity makes use of an object that it has previously found or discovered.
-
B.
usesReferenceObjects
Indicates that an entity performs an action or makes a determination by relying on one or more other entities as reference points or benchmarks.
-
C.
notableObject
Indicates that an entity is especially significant, famous, or noteworthy as an object in a given context or domain.
-
D.
objet
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
-
E.
hasObject
chosen
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2aee6881909fd28547f135427c |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.