Triple
T6588222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rarámuri language |
E159279
|
entity |
| Predicate | hasPersonMarking |
P50348
|
FINISHED |
| Object | on verbs |
—
|
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: on verbs | Statement: [Rarámuri language, hasPersonMarking, on verbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonMarking Context triple: [Rarámuri language, hasPersonMarking, on verbs]
-
A.
hasPersonMarkingOnVerb
chosen
Indicates that the verb carries explicit grammatical marking that identifies or agrees with the person (e.g., first, second, third person) of its subject or argument.
-
B.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
C.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
-
D.
hasMeasurementMarkings
Indicates that one entity bears visible measurement indicators or scale markings on its surface for quantifying something.
-
E.
hasMarker
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.