Triple
T32760963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Planet |
E837751
|
entity |
| Predicate | hasTemporalState |
P116906
|
FINISHED |
| Object | past |
—
|
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: past | Statement: [Little Planet, hasTemporalState, past]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalState Context triple: [Little Planet, hasTemporalState, past]
-
A.
hasTemporalBehavior
Indicates that an entity exhibits a particular pattern, characteristic, or change in behavior over time.
-
B.
hasTemporalAttribute
chosen
Indicates that an entity is associated with a specific temporal property or characteristic, such as time, duration, or period.
-
C.
hasTemporalDefinition
Indicates that something is associated with a definition or specification that is constrained or characterized by time.
-
D.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
-
E.
hasTemporalExpectation
Indicates that one entity holds an expectation about when (in time) another event, state, or action will occur or be valid.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 1:13 a.m.