Triple
T22007057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Part-Kneazle |
E543473
|
entity |
| Predicate | isCrossBetween |
P146249
|
FINISHED |
| Object | cat |
—
|
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: cat | Statement: [Part-Kneazle, isCrossBetween, cat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCrossBetween Context triple: [Part-Kneazle, isCrossBetween, cat]
-
A.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
-
B.
isKeyCrossingFor
Indicates that one entity serves as a primary or critical crossing point (such as a bridge, intersection, or passage) for another entity’s movement or connectivity.
-
C.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
D.
crossesOverWith
Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
-
E.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a18c1081909d15aa7ed4b725e3 |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:21 p.m.