Triple
T21805572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US9497461015 |
E538340
|
entity |
| Predicate | hasMaturityDate |
P145716
|
FINISHED |
| Object | Unknown |
—
|
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: Unknown | Statement: [US9497461015, hasMaturityDate, Unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaturityDate Context triple: [US9497461015, hasMaturityDate, Unknown]
-
A.
hasMaturity
Indicates that an entity possesses a specified level, state, or stage of development or maturity.
-
B.
hasMaturityType
Indicates that an entity is associated with a specific type or category of maturity it possesses or reaches.
-
C.
mustBeMaturedIn
Indicates that something is required to undergo a maturation process within a specified context, condition, or environment before it is considered ready or valid.
-
D.
maturityType
Indicates the kind or category of maturity associated with an entity, such as how or when an obligation, product, or process reaches its full or due state.
-
E.
maturesIn
Indicates that an entity reaches full development, ripeness, or maturity within a specified time period or under certain conditions.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07802bffc8190b383a2c89de75f74 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:53 p.m.