Triple
T7111427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form R |
E165714
|
entity |
| Predicate | isMoreDetailedThan |
P28230
|
FINISHED |
| Object | Form A |
—
|
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: Form A | Statement: [Form R, isMoreDetailedThan, Form A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMoreDetailedThan Context triple: [Form R, isMoreDetailedThan, Form A]
-
A.
isMoreSpecificThan
chosen
Indicates that one concept represents a narrower, more detailed, or more constrained case of another concept.
-
B.
isDeeperThan
Indicates that one entity has a greater depth or is positioned further down than another entity.
-
C.
isCoarserThan
Indicates that one entity has a lower level of detail or granularity than another, representing a broader or less refined characterization or partition.
-
D.
isExtendedVersionOf
Indicates that one entity is a longer or more developed form of another, typically adding content or features while preserving the original’s core.
-
E.
isAbstractVersionOf
Indicates that one entity represents a conceptual, generalized, or non-concrete version of another, more specific or concrete entity.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.