Triple
T19133247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (2014) FT71 |
E468368
|
entity |
| Predicate | hasPhysicalCategory |
P15481
|
FINISHED |
| Object | small Solar System body |
—
|
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: small Solar System body | Statement: [(2014) FT71, hasPhysicalCategory, small Solar System body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalCategory Context triple: [(2014) FT71, hasPhysicalCategory, small Solar System body]
-
A.
hasPhysicalLocationType
Indicates that an entity is associated with a specific kind or category of physical location (e.g., building type, facility type, or place type).
-
B.
hasPhysicalNature
Indicates that one entity possesses or exhibits a specific physical form, composition, or material nature in relation to another.
-
C.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
D.
hasSpecialCategory
Indicates that an entity is associated with a designated special or exceptional category distinct from its standard classifications.
-
E.
isPhysicalArtifact
Indicates that the subject is a tangible, man-made object that physically exists in the real world.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3eb325081909035beefd1c9daf0 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.