Triple
T33509419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferret Face |
E858198
|
entity |
| Predicate | settingConflictContext |
P56733
|
FINISHED |
| Object | Korean War |
—
|
NE NERFINISHED |
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: Korean War | Statement: [Ferret Face, settingConflictContext, Korean War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingConflictContext Context triple: [Ferret Face, settingConflictContext, Korean War]
-
A.
settingConflict
Indicates a conflict or incompatibility between two settings, configurations, or environmental conditions.
-
B.
conflictContext
Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
-
C.
settingOfConflict
chosen
Indicates the location or context in which a conflict between entities takes place.
-
D.
conflictOfEstablishmentContext
Indicates that there is a disagreement, incompatibility, or clash within the situational or institutional context in which something is established or set up.
-
E.
valueConflict
Indicates a situation where two or more values, preferences, or principles are in opposition or cannot be simultaneously satisfied.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:38 a.m.