Triple
T15385349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finn |
E367901
|
entity |
| Predicate | showsPotentialFor |
P58576
|
FINISHED |
| Object | Force sensitivity |
—
|
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: Force sensitivity | Statement: [Finn, showsPotentialFor, Force sensitivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsPotentialFor Context triple: [Finn, showsPotentialFor, Force sensitivity]
-
A.
hasPotential
chosen
Indicates that an entity possesses the capacity or possibility to develop, achieve, or exhibit a particular state, quality, or outcome in the future.
-
B.
exportPotential
Indicates the extent to which something is suitable or likely to be successfully exported to other markets or locations.
-
C.
hasSequelPotential
Indicates that a work or story has qualities suggesting it could be continued or expanded in a subsequent installment.
-
D.
agingPotential
Indicates the capacity or suitability of something to improve, develop, or remain effective over time as it ages.
-
E.
hasSpinOffPotential
Indicates that an entity (such as a project, product, or idea) has the capacity to be developed into a separate, independent venture or derivative offering.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e74ff70819094c1a85f51d6e228 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.