Triple
T20726877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alec Hardy |
E509458
|
entity |
| Predicate | isDetermined |
P2704
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Alec Hardy, isDetermined, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDetermined Context triple: [Alec Hardy, isDetermined, true]
-
A.
determined
chosen
Indicates that an entity has firmly decided on a course of action or conclusion, typically after consideration or effort.
-
B.
determinedBy
Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
-
C.
statusDetermines
Indicates that the status or condition of one entity determines or governs the state, outcome, or behavior of another entity.
-
D.
isDeterministic
Indicates that the outcome of a process or function is fully determined by its inputs, with no randomness or variation between executions.
-
E.
hasDeterminant
Indicates that one entity functions as a determiner (e.g., article, demonstrative, quantifier) specifying or limiting the reference of another entity, typically a noun or noun phrase.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e8b020819091d5788b90215ead |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:29 p.m.