Triple
T1399841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iyaric |
E30752
|
entity |
| Predicate | hasSemanticStrategy |
P10782
|
FINISHED |
| Object | reanalysis of English morphemes |
—
|
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: reanalysis of English morphemes | Statement: [Iyaric, hasSemanticStrategy, reanalysis of English morphemes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSemanticStrategy Context triple: [Iyaric, hasSemanticStrategy, reanalysis of English morphemes]
-
A.
usesStrategy
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
B.
hasElectoralStrategy
Indicates that an entity employs or is associated with a specific plan or approach for winning or influencing an election.
-
C.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
D.
hasApproachType
chosen
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
E.
hasNotableSegment
Indicates that an entity includes or contains a specific segment, part, or portion that is considered notable or significant in some way.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39c4c148190997150996ca26a99 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.