Triple
T7567482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Healy |
E178952
|
entity |
| Predicate | relationshipToHollandMarch |
P77648
|
FINISHED |
| Object | reluctant partner |
—
|
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: reluctant partner | Statement: [Jackson Healy, relationshipToHollandMarch, reluctant partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHollandMarch Context triple: [Jackson Healy, relationshipToHollandMarch, reluctant partner]
-
A.
joinedUnionOfUtrecht
Indicates that an entity became a member or signatory of the Union of Utrecht.
-
B.
joinedBelgiumFrom
Indicates that an entity became a member of or entered into Belgium from another specified entity or jurisdiction.
-
C.
relationshipToState
Indicates a relationship or connection that an entity has with a particular state or governmental body.
-
D.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
E.
memberOfThroughCountry
Indicates that an entity is a member of another entity (such as an organization or group) by virtue of, or via, its association with a specific country.
- F. None of above. chosen
Provenance (4 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f91c717881909c88901cc3b101c7 |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f59517648190ac0a9e9cba045dd5 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:51 p.m.