Triple
T7407988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomini–Tolitoli languages |
E170927
|
entity |
| Predicate | shareInnovation |
P7447
|
FINISHED |
| Object | common lexical innovations within Celebic |
—
|
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: common lexical innovations within Celebic | Statement: [Tomini–Tolitoli languages, shareInnovation, common lexical innovations within Celebic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareInnovation Context triple: [Tomini–Tolitoli languages, shareInnovation, common lexical innovations within Celebic]
-
A.
sharesInnovationWith
Indicates that one entity shares or exchanges innovative ideas, methods, or technologies with another entity.
-
B.
sharesTechnologyWith
Indicates that one entity provides, exchanges, or jointly uses technology with another entity.
-
C.
shareFeature
chosen
Indicates that two or more entities possess at least one common attribute, property, or characteristic.
-
D.
sharesPlatformWith
Indicates that two entities operate on, are available through, or participate within the same platform or system.
-
E.
share
Indicates that one entity gives, divides, or jointly uses a resource, item, or information with another entity.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f298f2388190afc944c9bc78749a |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.