Triple
T22555144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerberos |
E557659
|
entity |
| Predicate | tidalLocking |
P27809
|
FINISHED |
| Object | not tidally locked to Pluto |
—
|
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: not tidally locked to Pluto | Statement: [Kerberos, tidalLocking, not tidally locked to Pluto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tidalLocking Context triple: [Kerberos, tidalLocking, not tidally locked to Pluto]
-
A.
tidalLock
chosen
Indicates that one astronomical body always shows the same face to another because its rotational period matches its orbital period around that body.
-
B.
regionLocking
Indicates that access to or use of something is restricted based on the geographic region of the user or device.
-
C.
requiresLock
Indicates that performing the associated action or accessing the related resource is contingent on acquiring a lock to ensure exclusive or synchronized use.
-
D.
usesLockSystem
Indicates that one entity employs or relies on a locking mechanism or lock-based system provided by another entity.
-
E.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f78d8288190871d54db0a7f454b |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.