Triple
T5247785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman territorial expansion |
E118506
|
entity |
| Predicate | hasDrivingFactor |
P24726
|
FINISHED |
| Object | military conquest |
—
|
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: military conquest | Statement: [Ottoman territorial expansion, hasDrivingFactor, military conquest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingFactor Context triple: [Ottoman territorial expansion, hasDrivingFactor, military conquest]
-
A.
drivingForce
chosen
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
B.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
C.
hasSteering
Indicates that one entity is equipped with or possesses a steering mechanism that allows control of its direction.
-
D.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
E.
driveAssistFeature
Indicates that one entity provides an assistance feature that helps another entity perform driving-related tasks.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b77165c8190bd1ce8a197cef226 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.