Triple
T10884577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipan language |
E257008
|
entity |
| Predicate | hasSubjectObjectMarking |
P96227
|
FINISHED |
| Object | on verb complex |
—
|
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 verb complex | Statement: [Lipan language, hasSubjectObjectMarking, on verb complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectObjectMarking Context triple: [Lipan language, hasSubjectObjectMarking, on verb complex]
-
A.
hasSecurityClass
Indicates that an entity is assigned to or associated with a particular security classification level.
-
B.
hasSecurityRelationship
Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of another entity.
-
C.
hasComplianceObjective
Indicates that an entity is associated with, or aims to fulfill, a specific compliance-related objective or requirement.
-
D.
hasSubjectPosition
Indicates that an entity occupies or is assigned to a particular subject role or position within a structure, context, or organization.
-
E.
hasMetaSubject
Indicates that an entity is associated with a subject at a meta-level, such as the topic, theme, or aboutness of the entity rather than its direct content or participants.
- F. None of above. chosen
Provenance (4 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751dc3518819090e03d81ea5c8aa9 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101de31c819090707635f6790559 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.