Triple
T31418462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kroon |
E801463
|
entity |
| Predicate | requiresContextForDisambiguation |
P197201
|
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: [Kroon, requiresContextForDisambiguation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresContextForDisambiguation Context triple: [Kroon, requiresContextForDisambiguation, true]
-
A.
requiresDisambiguationInContext
chosen
Indicates that the referenced item is ambiguous and needs additional contextual information to be correctly interpreted or distinguished from similar items.
-
B.
requiresDisambiguationIn
Indicates that an entity is ambiguous and needs clarification or distinction specifically within the context of a given language, domain, or environment.
-
C.
requiresDisambiguationOn
Indicates that the referenced entity is ambiguous and needs additional clarification or context specifically on the associated item or dimension.
-
D.
requiresDisambiguationFrom
Indicates that one entity needs to be distinguished or clarified in relation to another similar or potentially confusing entity.
-
E.
requiresAdditionalDisambiguation
Indicates that the referenced entity or relationship is not sufficiently specific and needs further clarification or distinguishing information to avoid confusion with similar entities or meanings.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 30, 2026, 8:46 p.m.