Triple
T25777280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fagauvea |
E649185
|
entity |
| Predicate | isSubjectOfField |
P70296
|
FINISHED |
| Object | Oceanic linguistics |
—
|
NE NERFINISHED |
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: Oceanic linguistics | Statement: [Fagauvea, isSubjectOfField, Oceanic linguistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubjectOfField Context triple: [Fagauvea, isSubjectOfField, Oceanic linguistics]
-
A.
fieldRepresents
Indicates that one field or attribute stands for, encodes, or symbolizes another concept, value, or entity.
-
B.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
C.
immediateSubjectOf
Indicates that one entity is the direct grammatical subject of another entity (typically a clause, phrase, or verb), without any intervening subject relations.
-
D.
isFixedFieldOf
Indicates that one element is a fixed, non-variable field or attribute that belongs to and is structurally defined as part of another entity.
-
E.
isSubjectOfStudy
chosen
Indicates that an entity is the focus or topic being examined, researched, or analyzed in a study or investigation.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 22, 2026, 5:35 a.m.