Triple
T23333214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freedom Fighter |
E591501
|
entity |
| Predicate | isExportOrientedDesign |
P151898
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Freedom Fighter, isExportOrientedDesign, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExportOrientedDesign Context triple: [Freedom Fighter, isExportOrientedDesign, true]
-
A.
isExported
Indicates that an entity is sent out or transferred from its origin to an external destination or system.
-
B.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
C.
isExportable
Indicates that something can be legally and practically transferred or sent out from one jurisdiction, system, or context to another.
-
D.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
E.
hasDesignIntent
Indicates that one entity embodies or reflects the planned purpose, function, or conceptual intent defined by another entity.
- F. None of above. chosen
Provenance (4 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197eecc5c81908089eb43bc701196 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:16 p.m.