Triple
T7591824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtic cross |
E179751
|
entity |
| Predicate | hasGeometricFeature |
P25627
|
FINISHED |
| Object | circle intersecting cross arms |
—
|
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: circle intersecting cross arms | Statement: [Celtic cross, hasGeometricFeature, circle intersecting cross arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeometricFeature Context triple: [Celtic cross, hasGeometricFeature, circle intersecting cross arms]
-
A.
hasGeometry
chosen
Indicates that an entity is associated with a specific geometric representation or spatial form.
-
B.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
-
C.
hasFeatureClass
Indicates that an entity is associated with, or categorized under, a particular feature class that characterizes its type or nature.
-
D.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
-
E.
hasGeodesics
Indicates that the subject possesses or is characterized by geodesic paths, typically representing shortest or straightest possible routes within a given space or geometry.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b746ac8190b255afdfb9635f72 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.