Triple
T31218463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LS3 |
E795935
|
entity |
| Predicate | autonomyLevel |
P5082
|
FINISHED |
| Object | semi-autonomous |
—
|
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: semi-autonomous | Statement: [LS3, autonomyLevel, semi-autonomous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomyLevel Context triple: [LS3, autonomyLevel, semi-autonomous]
-
A.
hadAutonomyLevel
Indicates the degree of independence or decision-making freedom an entity was allowed or exercised in a given context.
-
B.
autonomyStatus
chosen
Indicates the degree to which an entity operates independently or with self-governed control, without external direction or intervention.
-
C.
autonomyDemand
Indicates a request or assertion by one party to have independent control or self-governance in a situation or relationship.
-
D.
hasAutonomyWithin
Indicates that one entity possesses independent decision-making power or self-governance within the scope, domain, or boundaries defined by another entity.
-
E.
hasAutonomyOver
Indicates that one entity possesses independent control, decision-making power, or self-governance with respect to another entity or domain.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c4a700c81908ee61dcb01bffe50 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.