Triple
T38178544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Gore, 1st Earl of Arran |
E1000284
|
entity |
| Predicate | title rank |
P152574
|
FINISHED |
| Object | earl |
—
|
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: earl | Statement: [Arthur Gore, 1st Earl of Arran, title rank, earl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: title rank Context triple: [Arthur Gore, 1st Earl of Arran, title rank, earl]
-
A.
rankOfHead
Indicates the hierarchical level or status assigned to the head (leader) of an entity within an ordered ranking system.
-
B.
rankIn
chosen
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
-
C.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
D.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
E.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: May 3, 2026, 4:29 p.m.