Triple
T17150303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Foix |
E416201
|
entity |
| Predicate | eventualIntegration |
P120479
|
FINISHED |
| Object | French royal domain |
—
|
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: French royal domain | Statement: [Count of Foix, eventualIntegration, French royal domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventualIntegration Context triple: [Count of Foix, eventualIntegration, French royal domain]
-
A.
eventuallyIn
chosen
Indicates that one entity will, at some later time or in the long run, come to be located in, belong to, or be contained within another entity or state.
-
B.
seeksToIntegrate
Indicates an effort or intention by one entity to combine, unify, or harmonize itself or its components with another entity or system.
-
C.
previouslyIntegratedInto
Indicates that an entity was formerly incorporated or included as part of another entity or system in the past.
-
D.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
E.
integrationFeature
Indicates that one entity provides a capability or component specifically intended to enable or support integration with another system, service, or component.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f4067470819084aa233c4c4a6d4f |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.