Triple
T38402710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhaarar |
E900942
|
entity |
| Predicate | alsoEffectiveAtDistance |
P190845
|
FINISHED |
| Object | 6.5 furlongs |
—
|
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: 6.5 furlongs | Statement: [Muhaarar, alsoEffectiveAtDistance, 6.5 furlongs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoEffectiveAtDistance Context triple: [Muhaarar, alsoEffectiveAtDistance, 6.5 furlongs]
-
A.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
B.
isDistant
Indicates that one entity is far away or separated by a large distance from another entity.
-
C.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
D.
effectiveWithin
Indicates that one entity (such as a rule, condition, or effect) is valid, applicable, or in force only during a specified time period or within a defined contextual boundary.
-
E.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.