Triple
T2378422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auslan |
E46254
|
entity |
| Predicate | notDerivedFrom |
P38827
|
FINISHED |
| Object | spoken English |
—
|
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: spoken English | Statement: [Auslan, notDerivedFrom, spoken English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notDerivedFrom Context triple: [Auslan, notDerivedFrom, spoken English]
-
A.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
C.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
-
D.
notImplementedBy
Indicates that a specified functionality, specification, or feature is *not* realized or provided by the referenced entity (such as a system, component, or implementation).
-
E.
notFunction
Indicates that the specified entity does not serve as a function or is not used in a functional role within the given context.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abca4c937c8190b4dfca716b868d4f |
completed | March 7, 2026, 6:48 a.m. |
Created at: March 4, 2026, 7:57 p.m.