Triple
T9958398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirigo |
E195500
|
entity |
| Predicate | hasWordType |
P89228
|
FINISHED |
| Object | verb phrase |
—
|
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: verb phrase | Statement: [Dirigo, hasWordType, verb phrase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWordType Context triple: [Dirigo, hasWordType, verb phrase]
-
A.
appliesToWordType
chosen
Indicates that something is relevant or specifically pertains to a particular type or category of word.
-
B.
hasLanguageType
Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
-
C.
hasRootWord
Indicates that one linguistic form is derived from, based on, or directly associated with a specified root word.
-
D.
hasPhonologicalType
Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6cec7dc8190bb7e43c82a317707 |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.