Triple
T19429641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Towa language |
E486074
|
entity |
| Predicate | hasCommunityControlOverDocumentation |
P98352
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [Towa language, hasCommunityControlOverDocumentation, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityControlOverDocumentation Context triple: [Towa language, hasCommunityControlOverDocumentation, strong]
-
A.
hasCommunityControl
chosen
Indicates that authority or decision-making power over something is held collectively by a local community or community-based group.
-
B.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
C.
commonsControl
Indicates that one entity has authority or regulatory power over shared or common resources involving another entity.
-
D.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
-
E.
hasCommunityResource
Indicates that an entity provides, contains, or is associated with a resource intended for use by a community.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6321b78d08190b86cef7c60cbb61c |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.