Triple
T28610266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yama |
E724151
|
entity |
| Predicate | ptraceScopeValue |
P163562
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Yama, ptraceScopeValue, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ptraceScopeValue Context triple: [Yama, ptraceScopeValue, 0]
-
A.
scopeValue
chosen
Indicates that one entity specifies or constrains the quantitative or qualitative extent (scope) applicable to another entity or context.
-
B.
traceProperty
Indicates that a property or attribute of an entity is being tracked, recorded, or monitored over time or through a process.
-
C.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
D.
traceMapTo
Indicates a relationship where one entity is mapped or linked to another through a trace or tracking association, often to record or follow its origin, transformation, or correspondence.
-
E.
trace
Indicates following or mapping the path, origin, or development of something step by step through evidence or markers.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:29 a.m.