Triple
T38538252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MdCN |
E924756
|
entity |
| Predicate | launchDomain |
P71612
|
FINISHED |
| Object | naval |
—
|
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: naval | Statement: [MdCN, launchDomain, naval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchDomain Context triple: [MdCN, launchDomain, naval]
-
A.
launchEntity
chosen
Indicates initiating the start, deployment, or release of an entity into operation or into a new state or environment.
-
B.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
C.
controlDomain
Indicates that one entity has authority over, manages, or regulates the scope, behavior, or operations of another entity or system.
-
D.
transportDomain
Indicates a relationship where an entity operates or functions within the domain or context of transportation activities or systems.
-
E.
executionDomain
Indicates the context, environment, or scope within which an action, process, or operation is carried out or 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:32 p.m.